Release 10.1A: OpenEdge Development:
Progress Dynamics Managers API Reference

Overview

The Security Manager aids in the definition of security allocations and in applying those allocations at run time. Security allocations are grants or restrictions of privileges for specific users. Security allocations can be defined on:

Actions, which restrict access to UI controls such as toolbar buttons and tabs in a tab folder.
Restricted entities and fields in a database, including calculated fields.
Restricted ranges of data values in a particular field.
Restricted database records filtered in any way.
Restricted containers, menu structures, menu items, and login companies.

In a distributed environment, the Security Manager is started on both the client and server sides. There is a wrapper program for each side that sets the global variable, server-side, to either YES for the server-side version or NO for the client-side version. Both programs then include the main code of the manager from the af\app\afsecmngrp.i include file. The differences in how the manager operates on each side are triggered by checking the value of the server-side variable.

The Security Manager’s handle is stored in the global shared variable, gshSecurityManager.

Table 9–1 shows the files that contain the Security Manager’s code.

Table 9–1: Security Manager files

Type	Path
Client-side wrapper	af\sup2\afsecclntp.p
Server-side wrapper	af\app\afsecsrvrp.p
Main code	af\app\afsecmngrp.i
Included files	af\app\afsecgtsecctrlp.i af\app\afsecttdef.i af\app\afttsecurityctrl.i af\app\afsecupdusrallocp.i af\app\usrSecChck.i af\sup2\aferrortxt.i af\sup2\afglobals.i

For more information on this Manager, see the chapter on using the Progress Dynamics Managers in OpenEdge Development: Progress Dynamics Advanced Development .